Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

test: only include required networks for e2e tests #2149

Merged
merged 31 commits into from
Jan 14, 2025
Merged

Conversation

dewanshparashar
Copy link
Contributor

@dewanshparashar dewanshparashar commented Dec 17, 2024

Closes FS-1070

@cla-bot cla-bot bot added the cla-signed label Dec 17, 2024
Copy link

vercel bot commented Dec 17, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated (UTC)
arbitrum-token-bridge ✅ Ready (Inspect) Visit Preview Jan 14, 2025 1:20pm

@dewanshparashar dewanshparashar changed the title ci: only include local chains in CI ci: only include required networks in CI Dec 25, 2024
@dewanshparashar dewanshparashar marked this pull request as ready for review December 25, 2024 15:15
@dewanshparashar dewanshparashar changed the title ci: only include required networks in CI ci: include only required networks in CI Dec 25, 2024
@dewanshparashar dewanshparashar marked this pull request as ready for review December 27, 2024 12:05
brtkx
brtkx previously approved these changes Dec 27, 2024
@@ -16,5 +16,8 @@ export function shortenTxHash(txHash: string) {
)}`
}

export const isE2eTestingEnvironment =
typeof window !== 'undefined' && !!window.Cypress

export const isTestingEnvironment =
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There's 2 places where we use isTestingEnvironment:

  • in ProjectListing.tsx to display some dummy data
  • in setup.ts to configure chains

I think what we really need is isDevelopmentEnvironment because both of these use cases really depend on that. Having both isE2eTestingEnvironment and isTestingEnvironment is confusing.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah, good name isDevelopmentEnvironment ! Even I felt having isE2eTestingEnvironment and isTestingEnvironment was not optimal but couldn't come up with the perfect naming. Ty!

@spsjvc spsjvc changed the title ci: include only required networks in E2E tests test: only include required networks for e2e tests Jan 14, 2025
@spsjvc spsjvc enabled auto-merge (squash) January 14, 2025 14:00
@spsjvc spsjvc merged commit 17f1b88 into master Jan 14, 2025
78 of 85 checks passed
@spsjvc spsjvc deleted the fix-e2e-ci-no-list branch January 14, 2025 14:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants